fix(a2ml): reconcile media type to application/vnd.a2ml — unblocks IANA submission - #554
Merged
Merged
Conversation
…NA submission
The repo carried FOUR competing media-type names: application/vnd.a2ml (27
uses, incl. the completed IANA application), text/a2ml (5),
application/vnd.a2ml+text (3) and application/a2ml (1). The naming decision was
already made — a2ml/IANA-MEDIA-TYPE-APPLICATION.md is a finished RFC 6838
vendor-tree application for application/vnd.a2ml (rev 2, "ready for
submission") — but four files never caught up, and a submission contradicted by
its own normative spec invites expert-review pushback.
Reconciled to the application docs name in:
- a2ml/SPEC.adoc (x2: media-type table + IANA Considerations)
- a2ml/site/spec.md (application/a2ml is a standards-tree name that would
need IETF review, not the vendor tree we are applying under)
- a2ml/READINESS.md (+text is not a registered structured-syntax suffix
under RFC 6838 4.2.8)
Deliberately NOT touched: a2ml/archive/SPEC-v1.0.0.adoc (frozen historical
record) and a2ml/RECORD-DIALECT-SPEC.adoc 14, which knowingly documents the
inconsistency and defers resolution to the maintainers — update that section
once IANA assigns the type.
REGISTRY.a2ml regenerated (SPEC.adoc is registry-tracked); build-registry.sh
--check and build-scorecards.sh --check --strict both pass.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
CI failed: CI failures caused by a stale machine-readable registry file after media type reconciliation, a banned Python script in the repository, and a missing allowed-actions script in workflow initialization.OverviewAnalysis of 3 failed CI logs reveals 3 distinct issues: a registry drift failure directly related to the PR's media type changes, a repository governance violation due to a committed Python file, and a configuration issue where an action policy script path was not found. FailuresMachine-Readable Registry Drift (confidence: high)
Banned Language Policy Violation (confidence: high)
Missing Actions Policy Script (confidence: high)
Summary
Code Review ✅ ApprovedReconciles the media type references across documentation and the normative spec to application/vnd.a2ml in preparation for IANA submission. No issues found.
Tip Comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
hyperpolymath
disabled auto-merge
July 28, 2026 14:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clears the last in-repo blocker to the IANA media-type submission.
What I found
a2ml/IANA-MEDIA-TYPE-APPLICATION.mdis a complete, 259-line RFC 6838 vendor-tree application forapplication/vnd.a2ml(rev 2, 2026-04-03, "Status: Draft — ready for submission"). Its own checklist already ticks fields reviewed, spec links accessible, no naming conflict, and ASAM A2L (application/A2L) distinction clarified. The only unticked items are submit the form → monitor review → record the assigned type.So the registration isn't months of work — it's an owner action (the IANA web form needs applicant identity). But the repo contradicted its own application in four places:
application/vnd.a2mltext/a2mlapplication/vnd.a2ml+text+textis not a registered structured-syntax suffix (RFC 6838 §4.2.8)application/a2mlA submission contradicted by its own normative spec invites expert-review pushback, so this reconciles all four to the application doc's name.
Deliberately not touched
a2ml/archive/SPEC-v1.0.0.adoc(×2) — frozen historical record; the old name is correct there.a2ml/RECORD-DIALECT-SPEC.adoc§14 — it knowingly documents the inconsistency and defers resolution to maintainers. Worth a small editorial update once IANA assigns the type.Verification
build-registry.sh --check✅ andbuild-scorecards.sh --check --strict✅ locally.REGISTRY.a2mlregenerated becauseSPEC.adocis registry-tracked — which also clears the registry drift currently red on main.K9's dominant name is
application/vnd.k9+nickel(41 uses vs 11 bareapplication/vnd.k9).+nickelalso does not appear in IANA's Structured Syntax Suffix registry. Verify before submitting K9 — if unregistered, register bareapplication/vnd.k9and keep+nickelas documentation, or pursue a separate suffix registration (slow; depends on upstream Nickel).